Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-86310 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.22] OCPBUGS-89236: Handle CA bundle aggregation delay by requeuing revocation

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-89236, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign muraee for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Why we need this on release-4.22

The CRR controller on release-4.22 has a bug where ensureNewSignerCertificatePropagated (line 736) and ensureOldSignerCertificateRevoked (line 1033) return requeue: false when the total-client-ca ConfigMap hasn't been updated yet. This causes the controller to stop reconciling and wait passively for an informer event or the 1-minute periodic resync, which can exceed the e2e test's 10-minute timeout on HA clusters with 3 KAS replicas.

This bug was introduced by commit 706a79490 (per-pod verification refactor) which is on release-4.22. The fix (changing requeue: false to requeue: true on two lines) ensures the controller actively polls for the total-client-ca update instead of sleeping.

Without this fix, TestCreateClusterHABreakGlassCredentials permafails in periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aks.

Bug: https://redhat.atlassian.net/browse/OCPBUGS-86310

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 35.45%. Comparing base (5cb8735) to head (cbe15ed).

@@              Coverage Diff              @@
##           release-4.22    #8746   +/-   ##
=============================================
  Coverage         35.45%   35.45%           
=============================================
  Files               767      767           
  Lines             93724    93724           
=============================================
+ Hits              33226    33230    +4     
+ Misses            57785    57781    -4     
  Partials           2713     2713           

/jira refresh

@bryan-cox: This pull request references Jira Issue OCPBUGS-89236, which is valid. The bug has been moved to the POST state.

/lgtm

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aks
/test e2e-aws
/test e2e-aws-upgrade-hypershift-operator
/test e2e-azure-self-managed
/test e2e-kubevirt-aws-ovn-reduced
/test e2e-v2-aws

/retest

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard.